The object model diagram is a graphical representation of all of the objects in AutoMindr and the paths that these objects can interact with each other.
User
The user object can have any number of the following roles:
Primary Driver
Secondary Driver
Buddy
Mechanic
The user object has the following attributes associated with it:
demographic information
experience/understanding level
ownership history
maintenance habits
Buddy List
Buddie list stores connections to other users.
Car
The car object has the following attributes:
Manufacturer specifications
Dashboard information such as gas mileage, warning lights, odometer
Information that can be measured or sensed such as fluid levels, status of hoses, noises
Prompt
The prompt object talks with the maintenance log to identify triggers at appropriate times and locations to prompt users. These prompts gather information from the user to store in the maintenance log. The prompt object queries and writes to the maintenance log often.
Maintenance Log
Maintenance log includes a history of the following:
log entry history (all recordings of car’s data with time of log)
user info with time of log/change
maintenance provider history including logs of ratings and reviews
Maintenance Provider
The maintenance provider is an object representing shops and mechanics in AutoMindr, and serves as the commercial-presence for Maintenance Providers in the system. Users can rate these providers at a shop or mechanic level. The maintenance provider object has the following attributes:
contact information
user ratings/reviews
accreditation
Mechanic Object
The mechanic object behaves like a business card in AutoMindr for individual mechanics. Users can rate individual mechanics in addition to the Maintenance Providers. Mechanics can take their ratings with them if they switch employment. The following attributes are associated with the Mechanic Object:
contact information
user ratings/reviews
qualifications such as experience, speciality, accreditation, and education
Actions Between Objects
Primary Driver to Car Interaction
This is a one to many relationship. A primary driver can have multiple cars, but a car can only have one primary driver. The primary driver drives and maintains the car and gathers information regarding the car’s status and health.
Secondary Driver to Car Interaction
This is a many to many relationship. A secondary driver can be listed under multiple cars, and a car can have multiple secondary drivers. The secondary driver has similar interactions with the car as the primary driver, but is not the person primarily responsible for the car.
Mechanic to Car Interaction
The mechanic performs maintenance and repair work on a car. The mechanic gets information regarding the car’s status and health and can change the status of the car physically and in the system.
User to Maintenance Log Interaction
The primary driver can view, search, and update the maintenance log. With permissions from the primary driver, the secondary driver and mechanic can also view and update the maintenance log.
Prompt to Primary/Secondary Driver
Reminds about maintenance
Teaches how to perform car maintenance.
Provides motivation.
Prompts user regarding missing data
Collects data via bite-size queries
Prompts are time and location dependent
Secondary driver is prompted by the system for that car only when they are driving and the primary driver is not present
Prompt to Maintenance Log
The prompt queries the maintenance log for triggers and updates the maintenance log with user feedback.
Prompt to Mechanic
The prompt asks the mechanic for updated car status after work is done on the car.
Optional Car to Maintenance Log Interaction
This interaction is optional at this time. There is a “magic hat” noted on the diagram for this interaction because the possibility of both of these objects interacting without help from an of the user objects is not yet known or cutting-edge.
Car sends information to the maintenance log directly by using the car’s computer.
Maintenance log pings car.
Driver to Maintenance Provider and Mechanic
The following interactions occur between drivers and maintenance providers in AutoMindr:
Driver can rate and review Maintenance Provider and/or individual mechanic at shop
Any user role can provide information about maintenance providers and mechanics that have not participated with AutoMindr
Drivers contact maintenance providers
Consultations between driver and maintenance provider
Maintenance Provider and Mechanic to Car Interaction
Maintenance providers can get the status of a car. After working on a car, the maintenance provider changes the status of the car as well.
Maintenance Provider and Mechanic to Maintenance Log Interaction
Maintenance providers can view and update the log with primary driver permission.
Driver to Buddy Interaction
Depending on the permissions Drivers’ give to their Buddies, the Buddy can view the following:
Buddies’ cars
Buddies’ logs
Buddies’ profile information
Buddies’ Maintenance Provider relationships
User to Buddy List Interaction
This is a list to search and browse buddies.
Bi-Products: Features from Data-Mining and Action-Mining
These are secondary features that arise as a result from User interactions in AutoMindr.
History of Maintenance Providers
History of User maintenance habits
Community Interactivity
System not dependent on User-initiated input
Granular Information Input
Car Maintenance History (carfax)
System able to generate alerts based off of input from:
User
Car
Mechanic
Able to transfer car ownership
Prompts are generated via environmental cues making learning of car maintenance habits more intuitive.
Requirements for Implementation
Based on our research, the objects, views, and actions need to have the following:
User input is small and unobtrusive (bite-size)
Prompts are time and location dependent
Allows for users to opt-in and out of assistance on a case by case basis
Objects
Figure 02: Object Model Diagram
User
The user object can have any number of the following roles:The user object has the following attributes associated with it:
Buddy List
Buddie list stores connections to other users.Car
The car object has the following attributes:Prompt
The prompt object talks with the maintenance log to identify triggers at appropriate times and locations to prompt users. These prompts gather information from the user to store in the maintenance log. The prompt object queries and writes to the maintenance log often.Maintenance Log
Maintenance log includes a history of the following:Maintenance Provider
The maintenance provider is an object representing shops and mechanics in AutoMindr, and serves as the commercial-presence for Maintenance Providers in the system. Users can rate these providers at a shop or mechanic level. The maintenance provider object has the following attributes:Mechanic Object
The mechanic object behaves like a business card in AutoMindr for individual mechanics. Users can rate individual mechanics in addition to the Maintenance Providers. Mechanics can take their ratings with them if they switch employment. The following attributes are associated with the Mechanic Object:Actions Between Objects
Primary Driver to Car Interaction
This is a one to many relationship. A primary driver can have multiple cars, but a car can only have one primary driver. The primary driver drives and maintains the car and gathers information regarding the car’s status and health.Secondary Driver to Car Interaction
This is a many to many relationship. A secondary driver can be listed under multiple cars, and a car can have multiple secondary drivers. The secondary driver has similar interactions with the car as the primary driver, but is not the person primarily responsible for the car.Mechanic to Car Interaction
The mechanic performs maintenance and repair work on a car. The mechanic gets information regarding the car’s status and health and can change the status of the car physically and in the system.User to Maintenance Log Interaction
The primary driver can view, search, and update the maintenance log. With permissions from the primary driver, the secondary driver and mechanic can also view and update the maintenance log.Prompt to Primary/Secondary Driver
Prompt to Maintenance Log
The prompt queries the maintenance log for triggers and updates the maintenance log with user feedback.Prompt to Mechanic
The prompt asks the mechanic for updated car status after work is done on the car.Optional Car to Maintenance Log Interaction
This interaction is optional at this time. There is a “magic hat” noted on the diagram for this interaction because the possibility of both of these objects interacting without help from an of the user objects is not yet known or cutting-edge.Driver to Maintenance Provider and Mechanic
The following interactions occur between drivers and maintenance providers in AutoMindr:Maintenance Provider and Mechanic to Car Interaction
Maintenance providers can get the status of a car. After working on a car, the maintenance provider changes the status of the car as well.Maintenance Provider and Mechanic to Maintenance Log Interaction
Maintenance providers can view and update the log with primary driver permission.Driver to Buddy Interaction
Depending on the permissions Drivers’ give to their Buddies, the Buddy can view the following:User to Buddy List Interaction
This is a list to search and browse buddies.Bi-Products: Features from Data-Mining and Action-Mining
These are secondary features that arise as a result from User interactions in AutoMindr.Requirements for Implementation
Based on our research, the objects, views, and actions need to have the following: